DXL in DWA

I see that Attr_DXL runs in DWA.  I'm trying to figure out how the Attr-DXL can detect it is running in DWA figuring to behave differently.  Any ideas?

So far these 3 indicators are different in DWA than in normal DOORS GUI (all part of the "doors.exe -interop" command line)

• bool runningAsInteropServer()    // this is the prime candicate now; I wonder if it may return "true" in some other context
• getenv("DOORSBROKERHOST")
• getenv("DOORSBROKERPORT")

So far these things are NOT different in DWA

• runningAsDoorsnet()    // always false
• getenv("DOORSINTEROP")  // always null
• getResourceURLConfigOptions(Prot, Host, Port)  // always "http", "", 8080)

These commands interpret OK, but get runtime DXL error "Perm no longer supported"

• User getInteropUser_()
• int      getRemotePort_()  
• string   getRemoteHost_()  
• int getInteropLocalDatabaseID_() 
• int getInteropLocalDatabaseID_() 
• string getRemoteWebservicePath_() 

Other notes of interest

• I see that if the DOORS client running on the server has "addins" defined, these relative paths are indeed used in DWA; thus Attr-DXL can have relative include files.
• Triggers do not run
• Layouts run
• There is some problem with my massive library vis-a-vis running Attr-DXL in DWA; I'm sure it is that I use some GUI functions not loaded in "interop" mode.

-Louie